PlantUML-MCP-Server

Created By
Mario Zagar9 months ago
A Model Context Protocol (MCP) server that provides PlantUML diagram generation capabilities for Claude Desktop and Claude Code.
Overview

What is PlantUML-MCP-Server?

PlantUML-MCP-Server is a Model Context Protocol (MCP) server that enables the generation of PlantUML diagrams for applications like Claude Desktop and Claude Code.

How to use PlantUML-MCP-Server?

To use the server, set it up in your Claude environment by adding the appropriate configuration to your MCP settings and restart the application.

Key features of PlantUML-MCP-Server?

  • Generate PlantUML diagrams and obtain embeddable SVG/PNG URLs.
  • Create various types of diagrams including sequence, class, and architecture diagrams.
  • Encode and decode PlantUML code for easy URL sharing.

Use cases of PlantUML-MCP-Server?

  1. Generating UML diagrams for software architecture documentation.
  2. Creating visual representations of system designs.
  3. Sharing encoded PlantUML diagrams via URLs for collaboration.

FAQ from PlantUML-MCP-Server?

  • What types of diagrams can I create?

You can create sequence diagrams, class diagrams, architecture diagrams, and more.

  • Is there a way to share diagrams easily?

Yes! You can encode PlantUML code into a URL for easy sharing.

  • What are the prerequisites for running the server?

You need Node.js 18+ and npm installed on your machine.

Server Config

{
  "mcpServers": {
    "plantuml": {
      "command": "npx",
      "args": [
        "plantuml-mcp-server"
      ],
      "env": {
        "PLANTUML_SERVER_URL": "https://www.plantuml.com/plantuml"
      }
    }
  }
}
Project Info
Created At
9 months ago
Updated At
9 months ago
Author Name
Mario Zagar
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago